Automatic upgrade from one step authentication to two step authentication via application programming interface

ABSTRACT

A client transmits a user identifier and a password to a server via an application programming interface (API). The client establishes an authenticated session with the server in which the client has a first set of permissions for operations associated with the API. The client receives, responsive to a verification of the user identifier and password by the server, a logon response and a shared secret. The client generates a one time passcode (OTP) based upon the shared secret. The client sends the OTP to the server via the API. Responsive to the server validating the OTP against the shared secret, the server grants a second set of permissions for operations associated with the API.

TECHNICAL FIELD

The present invention relates generally to a method, system, andcomputer program product for two step authentication. More particularly,the present invention relates to a method, system, and computer programproduct for automatic upgrade from one step authentication to two stepauthentication via an application programming interface.

BACKGROUND

Currently, network application security is being augmented from thestandard procedure of a user providing a user identifier (ID) andpassword in order to authenticate with a network service or applicationto further requiring a two step authentication process. In addition torequiring a user to provide a first authentication factor, such as auser ID and password, two step authentication requires the user toprovide a second authentication factor in order to complete anauthentication process. Typically, the second authentication factor isinformation known to the user that is unlikely to be known by anunauthorized user such as a secret known to the user or a securitytoken.

SUMMARY

The illustrative embodiments provide a method, system, and computerprogram product. An embodiment of a method includes transmitting, by aclient, a user identifier and a password to a server via an applicationprogramming interface (API). The embodiment further includesestablishing an authenticated session with the server in which theclient has a first set of permissions for operations associated with theAPI. The embodiment further includes receiving, responsive to averification of the user identifier and password by the server, a logonresponse and a shared secret. The embodiment further includesgenerating, by the client, a one time passcode (OTP) based upon theshared secret. The embodiment further includes sending the OTP to theserver via the API. The embodiment still further includes granting,responsive to the server validating the OTP against the shared secret, asecond set of permissions for operations associated with the API.

An embodiment further includes receiving, by the client device, the useridentifier and password, from a user. In an embodiment, the receiving ofthe logon response and shared secret is responsive to a determinationthat a user associated with the user identifier is designated forupgrading from one factor authentication to two factor authentication.

An embodiment further includes storing, by the client, the shared secretwithin client preferences associated with a user. In an embodiment, theserver is configured to store the shared secret within a user profileassociated with a user. In an embodiment, the API includes aRepresentational state transfer (REST) API. In an embodiment, the secondset of permissions is greater than the first set of permissions.

An embodiment further includes transmitting the user ID, the password,and a current OTP generated based upon the shared secret to the serverin a subsequent logon operation.

An embodiment includes a computer usable program product. The computerusable program product includes one or more computer-readable storagedevices, and program instructions stored on at least one of the one ormore storage devices.

An embodiment includes a computer system. The computer system includesone or more processors, one or more computer-readable memories, and oneor more computer-readable storage devices, and program instructionsstored on at least one of the one or more storage devices for executionby at least one of the one or more processors via at least one of theone or more memories.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofthe illustrative embodiments when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a block diagram of a network of data processing systemsin which illustrative embodiments may be implemented;

FIG. 2 depicts a block diagram of a data processing system in whichillustrative embodiments may be implemented;

FIG. 3 depicts a block diagram of an example configuration for automaticupgrade of two step authentication in accordance with an illustrativeembodiment;

FIG. 4 depicts a message flow of an example process for automaticupgrade of two step authentication in accordance with an illustrativeembodiment;

FIG. 5 depicts a flowchart of an example client side process forautomatic upgrade of two step authentication in accordance with anillustrative embodiment; and

FIG. 6 depicts a flowchart of an example server side process forautomatic upgrade of two step authentication in accordance with anillustrative embodiment.

DETAILED DESCRIPTION

Various illustrative embodiments provide for automatic upgrade from onestep to two step authentication for server applications or services thatutilize a stateless protocol application programming interface (API). Astateless protocol does not require either the sender or receiver toretain session information during the life of a communication session.One or more embodiments provide for automatic upgrade from one step totwo step authentication for server applications or services that utilizea Representational state transfer (REST) API completely in-band withoutrequiring additional steps outside of the REST API work area. Two stepauthentication is sometimes referred to as two factor authentication. Inparticular embodiments, one step authentication utilizing only a user IDand password for authentication is automatically upgraded for aparticular user to two step authentication utilizing a user ID/passwordas well as a one time passcode for authentication.

In a traditional use case for two factor authentication, a user logs onto a web application via a browser, enters a user ID and password, andenables two factor authentication within a user profile associated withthe user. The user then captures a shared secret with a smartphone orother device, commonly by scanning a QR code. The user generates apasscode based on the shared secret and submits the passcode to anauthenticating server for validation. In existing implementations, auser is required to set up the second factor in a traditional manner bylogging on via a web browser, and a separate authentication token, notthe same shared secret and algorithm, is used for web access compared toAPI access.

One or more particular embodiments described herein allows users thatinteract with a web application via REST APIs to leverage the same setof features that are available to a traditional web browser, that isenabling two step authentication for their user accounts, asauthentication via a REST API client.

In an embodiment, a particular user is designated as requiring anupgrade from one factor authentication to two factor authentication inorder to grant access to one or more applications or services at a nextlogon attempt. In a particular embodiment, the user is designated asrequiring two factor authentication by an administrator of anapplication or service. In the embodiment, a user logs on to a server,such as an authentication server, by providing a user ID and passwordusing a web services (REST API) client application. In the embodiment,the server attempts to verify the user using the user ID and password.

Upon successfully authentication, a session, such as a web servicessession, is established between the server and client in which the useris in a limited logged on state. In the limited logged on state, theuser is authenticated but only has permission to access a limited set ofAPI operations. In the embodiment, the server generates a shared secretand stores the shared secret within the session. In one or moreembodiments, the shared secret is information known only to the clientand server which is created using a key-agreement protocol such as apublic key encryption. In particular embodiments, the shared secret is apassword, passphrase or pseudo-randomly generated number or string. Inthe embodiment, the server sends a logged on response back to the clientcontaining session-specific data and the shared secret.

In the embodiment, the client application generates a one time passcode(OTP) based upon the shared secret. In a particular embodiment, the OTPis generated from the shared secret using a time-based one time passcode(TOTP) algorithm such as described in M′Raihi, D., Machani, S., Pei, M.,Rydell, J., “TOTP: Time-Based One-Time Password Algorithm”, Request forComments (RFC) 6238, Internet Engineering Task Force (IETF), May 2011.In one or more embodiments, the server combines the shared secret with acurrent timestamp using a cryptographic hash function to generate theone time passcode. In the embodiment, the client sends an API request tothe server including the OTP requesting setting of the shared secretinto a user profile associated with the user.

Responsive to receiving the OTP, the server validates that OTP againstthe shared secret. If validation is successful, the server stores theshared secret within the user profile and sends a successful responseback to the client. In the embodiment, the client application stores theshared secret into REST API client preferences or another database. Inthe embodiment, subsequent logons from the user require the user tosubmit the user ID, password, and a current OTP based on the sharedsecret in order to be authenticated with the server to gain access toapplications and services provided by the server.

The illustrative embodiments are described with respect to certain typesof services, transmissions, data processing systems, environments,components, and applications only as examples. Any specificmanifestations of these and other similar artifacts are not intended tobe limiting to the invention. Any suitable manifestation of these andother similar artifacts can be selected within the scope of theillustrative embodiments.

Furthermore, the illustrative embodiments may be implemented withrespect to any type of data, data source, or access to a data sourceover a data network. Any type of data storage device may provide thedata to an embodiment of the invention, either locally at a dataprocessing system or over a data network, within the scope of theinvention. Where an embodiment is described using a mobile device, anytype of data storage device suitable for use with the mobile device mayprovide the data to such embodiment, either locally at the mobile deviceor over a data network, within the scope of the illustrativeembodiments.

The illustrative embodiments are described using specific code, designs,architectures, protocols, layouts, schematics, and tools only asexamples and are not limiting to the illustrative embodiments.Furthermore, the illustrative embodiments are described in someinstances using particular software, tools, and data processingenvironments only as an example for the clarity of the description. Theillustrative embodiments may be used in conjunction with othercomparable or similarly purposed structures, systems, applications, orarchitectures. For example, other comparable mobile devices, structures,systems, applications, or architectures therefor, may be used inconjunction with such embodiment of the invention within the scope ofthe invention. An illustrative embodiment may be implemented inhardware, software, or a combination thereof.

The examples in this disclosure are used only for the clarity of thedescription and are not limiting to the illustrative embodiments.Additional data, operations, actions, tasks, activities, andmanipulations will be conceivable from this disclosure and the same arecontemplated within the scope of the illustrative embodiments.

Any advantages listed herein are only examples and are not intended tobe limiting to the illustrative embodiments. Additional or differentadvantages may be realized by specific illustrative embodiments.Furthermore, a particular illustrative embodiment may have some, all, ornone of the advantages listed above.

With reference to the figures and in particular with reference to FIGS.1 and 2, these figures are example diagrams of data processingenvironments in which illustrative embodiments may be implemented. FIGS.1 and 2 are only examples and are not intended to assert or imply anylimitation with regard to the environments in which differentembodiments may be implemented. A particular implementation may makemany modifications to the depicted environments based on the followingdescription.

FIG. 1 depicts a block diagram of a network of data processing systemsin which illustrative embodiments may be implemented. Data processingenvironment 100 is a network of computers in which the illustrativeembodiments may be implemented. Data processing environment 100 includesnetwork 102. Network 102 is the medium used to provide communicationslinks between various devices and computers connected together withindata processing environment 100. Network 102 may include connections,such as wire, wireless communication links, or fiber optic cables.

Clients or servers are only example roles of certain data processingsystems connected to network 102 and are not intended to exclude otherconfigurations or roles for these data processing systems. Server 104and server 106 couple to network 102 along with storage unit 108.Software applications may execute on any computer in data processingenvironment 100. Clients 110, 112, and 114 are also coupled to network102. A data processing system, such as server 104 or 106, or client 110,112, or 114 may contain data and may have software applications orsoftware tools executing thereon.

Only as an example, and without implying any limitation to sucharchitecture, FIG. 1 depicts certain components that are usable in anexample implementation of an embodiment. For example, servers 104 and106, and clients 110, 112, 114, are depicted as servers and clients onlyas example and not to imply a limitation to a client-serverarchitecture. As another example, an embodiment can be distributedacross several data processing systems and a data network as shown,whereas another embodiment can be implemented on a single dataprocessing system within the scope of the illustrative embodiments. Dataprocessing systems 104, 106, 110, 112, and 114 also represent examplenodes in a cluster, partitions, and other configurations suitable forimplementing an embodiment.

Device 132 is an example of a device described herein. For example,device 132 can take the form of a smartphone, a tablet computer, alaptop computer, client 110 in a stationary or a portable form, awearable computing device, or any other suitable device. Any softwareapplication described as executing in another data processing system inFIG. 1 can be configured to execute in device 132 in a similar manner.Any data or information stored or produced in another data processingsystem in FIG. 1 can be configured to be stored or produced in device132 in a similar manner.

Server application 105 of server 104 implements an embodiment of serverside authentication operations described herein. Database 109 may bestored in storage 108 as shown or supplied by another source (notshown). In particular embodiments, database 109 may store user profileinformation associated with one or more users. Client application 111implements an embodiment of client side authentication operationsdescribed herein.

Servers 104 and 106, storage unit 108, and clients 110, 112, and 114,and device 132 may couple to network 102 using wired connections,wireless communication protocols, or other suitable data connectivity.Clients 110, 112, and 114 may be, for example, personal computers ornetwork computers.

In the depicted example, server 104 may provide data, such as bootfiles, operating system images, and applications to clients 110, 112,and 114. Clients 110, 112, and 114 may be clients to server 104 in thisexample. Clients 110, 112, 114, or some combination thereof, may includetheir own data, boot files, operating system images, and applications.Data processing environment 100 may include additional servers, clients,and other devices that are not shown.

In the depicted example, data processing environment 100 may be theInternet. Network 102 may represent a collection of networks andgateways that use the Transmission Control Protocol/Internet Protocol(TCP/IP) and other protocols to communicate with one another. At theheart of the Internet is a backbone of data communication links betweenmajor nodes or host computers, including thousands of commercial,governmental, educational, and other computer systems that route dataand messages. Of course, data processing environment 100 also may beimplemented as a number of different types of networks, such as forexample, an intranet, a local area network (LAN), or a wide area network(WAN). FIG. 1 is intended as an example, and not as an architecturallimitation for the different illustrative embodiments.

Among other uses, data processing environment 100 may be used forimplementing a client-server environment in which the illustrativeembodiments may be implemented. A client-server environment enablessoftware applications and data to be distributed across a network suchthat an application functions by using the interactivity between aclient data processing system and a server data processing system. Dataprocessing environment 100 may also employ a service orientedarchitecture where interoperable software components distributed acrossa network may be packaged together as coherent business applications.Data processing environment 100 may also take the form of a cloud, andemploy a cloud computing model of service delivery for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (e.g. networks, network bandwidth, servers,processing, memory, storage, applications, virtual machines, andservices) that can be rapidly provisioned and released with minimalmanagement effort or interaction with a provider of the service.

With reference to FIG. 2, this figure depicts a block diagram of a dataprocessing system in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as servers104 and 106, or clients 110, 112, and 114 in FIG. 1, or another type ofdevice in which computer usable program code or instructionsimplementing the processes may be located for the illustrativeembodiments.

Data processing system 200 is also representative of a data processingsystem or a configuration therein, such as device 132 in FIG. 1 in whichcomputer usable program code or instructions implementing the processesof the illustrative embodiments may be located. Data processing system200 is described as a computer only as an example, without being limitedthereto. Implementations in the form of other devices, such as device132 in FIG. 1, may modify data processing system 200, such as by addinga touch interface, and even eliminate certain depicted components fromdata processing system 200 without departing from the generaldescription of the operations and functions of data processing system200 described herein.

In the depicted example, data processing system 200 employs a hubarchitecture including North Bridge and memory controller hub (NB/MCH)202 and South Bridge and input/output (I/O) controller hub (SB/ICH) 204.Processing unit 206, main memory 208, and graphics processor 210 arecoupled to North Bridge and memory controller hub (NB/MCH) 202.Processing unit 206 may contain one or more processors and may beimplemented using one or more heterogeneous processor systems.Processing unit 206 may be a multi-core processor. Graphics processor210 may be coupled to NB/MCH 202 through an accelerated graphics port(AGP) in certain implementations.

In the depicted example, local area network (LAN) adapter 212 is coupledto South Bridge and I/O controller hub (SB/ICH) 204. Audio adapter 216,keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224,universal serial bus (USB) and other ports 232, and PCI/PCIe devices 234are coupled to South Bridge and I/O controller hub 204 through bus 238.Hard disk drive (HDD) or solid-state drive (SSD) 226 and CD-ROM 230 arecoupled to South Bridge and I/O controller hub 204 through bus 240.PCI/PCIe devices 234 may include, for example, Ethernet adapters, add-incards, and PC cards for notebook computers. PCI uses a card buscontroller, while PCIe does not. ROM 224 may be, for example, a flashbinary input/output system (BIOS). Hard disk drive 226 and CD-ROM 230may use, for example, an integrated drive electronics (IDE), serialadvanced technology attachment (SATA) interface, or variants such asexternal-SATA (eSATA) and micro-SATA (mSATA). A super I/O (SIO) device236 may be coupled to South Bridge and I/O controller hub (SB/ICH) 204through bus 238.

Memories, such as main memory 208, ROM 224, or flash memory (not shown),are some examples of computer usable storage devices. Hard disk drive orsolid state drive 226, CD-ROM 230, and other similarly usable devicesare some examples of computer usable storage devices including acomputer usable storage medium.

An operating system runs on processing unit 206. The operating systemcoordinates and provides control of various components within dataprocessing system 200 in FIG. 2. The operating system may be acommercially available operating system for any type of computingplatform, including but not limited to server systems, personalcomputers, and mobile devices. An object oriented or other type ofprogramming system may operate in conjunction with the operating systemand provide calls to the operating system from programs or applicationsexecuting on data processing system 200.

Instructions for the operating system, the object-oriented programmingsystem, and applications or programs, such as server application 105 orclient application 111 in FIG. 1, are located on storage devices, suchas in the form of code 226A on hard disk drive 226, and may be loadedinto at least one of one or more memories, such as main memory 208, forexecution by processing unit 206. The processes of the illustrativeembodiments may be performed by processing unit 206 using computerimplemented instructions, which may be located in a memory, such as, forexample, main memory 208, read only memory 224, or in one or moreperipheral devices.

Furthermore, in one case, code 226A may be downloaded over network 201Afrom remote system 201B, where similar code 201C is stored on a storagedevice 201D. in another case, code 226A may be downloaded over network201A to remote system 201B, where downloaded code 201C is stored on astorage device 201D.

The hardware in FIGS. 1-2 may vary depending on the implementation.Other internal hardware or peripheral devices, such as flash memory,equivalent non-volatile memory, or optical disk drives and the like, maybe used in addition to or in place of the hardware depicted in FIGS.1-2. In addition, the processes of the illustrative embodiments may beapplied to a multiprocessor data processing system.

In some illustrative examples, data processing system 200 may be apersonal digital assistant (PDA), which is generally configured withflash memory to provide non-volatile memory for storing operating systemfiles and/or user-generated data. A bus system may comprise one or morebuses, such as a system bus, an I/O bus, and a PCI bus. Of course, thebus system may be implemented using any type of communications fabric orarchitecture that provides for a transfer of data between differentcomponents or devices attached to the fabric or architecture.

A communications unit may include one or more devices used to transmitand receive data, such as a modem or a network adapter. A memory may be,for example, main memory 208 or a cache, such as the cache found inNorth Bridge and memory controller hub 202. A processing unit mayinclude one or more processors or CPUs.

The depicted examples in FIGS. 1-2 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 200 also may be a tablet computer, laptop computer, or telephonedevice in addition to taking the form of a mobile or wearable device.

Where a computer or data processing system is described as a virtualmachine, a virtual device, or a virtual component, the virtual machine,virtual device, or the virtual component operates in the manner of dataprocessing system 200 using virtualized manifestation of some or allcomponents depicted in data processing system 200. For example, in avirtual machine, virtual device, or virtual component, processing unit206 is manifested as a virtualized instance of all or some number ofhardware processing units 206 available in a host data processingsystem, main memory 208 is manifested as a virtualized instance of allor some portion of main memory 208 that may be available in the hostdata processing system, and disk 226 is manifested as a virtualizedinstance of all or some portion of disk 226 that may be available in thehost data processing system. The host data processing system in suchcases is represented by data processing system 200.

With reference to FIG. 3, this figure depicts a block diagram of anexample configuration for automatic upgrade of two step authenticationin accordance with an illustrative embodiment. Client 302 is an exampleof client 110 in FIG. 1, and client application 306 is an example ofclient application 111 in FIG. 1. Server 304 is an example of server 104in FIG. 1, and server application 314 is an example of serverapplication 105 in FIG. 1. Network 300 is an example of network 102 inFIG. 1.

Client application 306 includes an authentication component 308, a RESTAPI component 310, and a client preferences component 312.Authentication component 308 is configured to perform client sideauthentication operations such as generating an OTP from a shared secretas described herein. REST API component 310 is configured to performREST-based message operations, such as between client 302 and server304, as described herein. Client preferences component 312 is configuredto store client preference information associated with a user 322 ofclient 302 such as a shared secret received from server 304 as describedherein.

Server application 314 includes an authentication component 316, a RESTAPI component 318, and a user profiles component 320. Authenticationcomponent 316 is configured to perform server side authenticationoperations such as generating a shared secret, validating a userID/password combination, and validating a given OTP against a sharedsecret as described herein. REST API component 318 is configured toperform REST-based message operations, such as between server 304 andclient 302, as described herein. User profiles component 320 isconfigured to store user profile information associated with user 322 ofclient 302 such as the shared secret generated by authenticationcomponent 316 as described herein.

In one embodiment, a process for two step authentication forapplications and services that utilize a REST API is provided in whichuser 322 provides a user ID and password to client application 306 ofclient 302, and client application 306 transits the user ID and passwordto server application 314 of server 304. In response to receiving theuser ID and password, server application 314 verifies the user ID andpassword. Upon successful verification of the user ID and password,server application 314 determines whether user 322 is to be upgradedfrom one step authentication to two step authentication. If user 322 isnot to be upgraded from one step authentication to two stepauthentication, server 304 establishes an authenticated session betweenclient 302 and server 304 having full permissions/access to APIoperations for client 302. If user 322 is to be upgraded from one stepauthentication to two step authentication, server 304 establishes anauthenticated session between client 302 and server 304 having limitedpermission with respect to permitted API operations for client 302.Server 304 sends a logon response including the shared secret generatedby authentication component 316 to client 302. Client 302 receives thelogin response including the shared secret and generates a one-timepasscode (OTP) based on the shared secret. Client 302 sends an APIrequest including the OTP to server 304 indicating that the sharedsecret is to be set into a user profile associated with user 322. Server304 receives the request including the OTP and validates the OTP againstthe shared secret. If server 304 successfully validates the OTP againstthe shared secret, server 304 continues the authenticated sessionbetween server 304 and client 302 in which client 302 is granted fullpermissions/access to API operations. Server 304 stores the sharedsecret within the user profile such that subsequent logons by clientapplication 306 require the user ID, the password, and a current OTPthat is generated based upon the shared secret.

With reference to FIG. 4, this figure depicts a message flow of anexample process for automatic upgrade of two step authentication inaccordance with an illustrative embodiment. In one or more embodiments,message flow 400 can be implemented in client application 306 and serverapplication 314 of FIG. 3.

In 402, client 302 receives a user ID and password from user 322. In404, client 302 sends the user ID and password to server 304. In 406,server 304 authenticates user 322 using a first authentication factor byvalidating the user ID and password. If user 322 is designated asrequiring upgrading from one step authentication to two stepauthentication, in 408 server 304 generates a shared secret andestablishes an authenticated session with client 302. In a particularembodiment, the authenticated session has limited permissions/access ofAPI operations for client 302. In 410, server 304 sends session-specificdata and the shared secret to client 302 using the authenticatedsession. In 412, client 302 generates a one time passcode (OTP) basedupon the shared secret. In 414, client 302 sends the OTP generated basedupon the shared secret to server 304.

In 416, server 304 validates the OTP against the shared secret. If theOTP is validated, in 418 server 304 stores the shared secret in a userprofile associated with user 322. In 420, server 304 sends anauthentication response to client 302 to continue the authenticatedsession in which client 302 has full permissions/access to APIoperations to receive access to applications and/or services provided byserver 304 or another server. In 422, client 302 stores the sharedsecret in client preferences component 312. Message flow 400 endsthereafter. In the embodiment, subsequent logons from user 322 requireuser 322 to provide the user ID, password, and a current OTP that isgenerated based on the shared secret in order to be authenticated withserver 304 to gain access to applications and services provided by theserver.

With reference to FIG. 5, this figure depicts a flowchart of an exampleclient side process for automatic upgrade of two step authentication inaccordance with an illustrative embodiment. In one or more embodiments,process 500 can be implemented in client application 306 in FIG. 3. In502, client application 306 prompts user 322 for a user ID and password.In 504, client application 306 receives the user ID and password fromuser 322. In 506, client application 306 sends the user ID and passwordto server 304.

If user 322 is designated as requiring upgrading from one stepauthentication to two step authentication, server 304 generates a sharedsecret. In block 508, client 302 establishes an authenticated sessionwith server 304. In a particular embodiment, the first authenticatedsession has limited permissions/access to API operations for client 302.In 510, client 302 receives a logon response including the shared secretfrom server 304 using the authenticated session.

In 512, client 302 generates a one time passcode (OTP) based upon theshared secret received from server 304. In 514, client 302 sends the OTPgenerated based upon the shared secret to server 304. Server 304validates the OTP against the shared secret. If the OTP is validated,server 304 stores the shared secret in a user profile associated withuser 322. In 516, client 302 receives an authentication response fromserver 304. In 518, client 302 determines whether the authenticationresponse indicates that user 322 is authenticated. If user 322 is notauthenticated, the process 500 ends. If user 322 is authenticated, in520 client 302 continues the authenticated session with server 304 inwhich client 302 is granted full permissions/access to API operations toreceive access to applications and/or services provided by server 304 oranother server. In 522, client 302 stores the shared secret in clientpreferences component 312. Client application 306 ends process 500thereafter. In the embodiment, subsequent logons from user 322 requireuser 322 to provide the user ID, password, and a current OTP that isgenerated based on the shared secret in order to be authenticated withserver 304 to gain access to applications and services provided by theserver.

With reference to FIG. 6, this figure depicts a flowchart of an exampleserver side process for automatic upgrade of two step authentication inaccordance with an illustrative embodiment. In one or more embodiments,process 600 can be implemented in server application 314 in FIG. 3. In602, server application 314 of server 304 receives a user ID andpassword provided by user 322 from client 302.

In 604, server application 314 authenticates user 322 using a firstauthentication factor by validating the user ID and password. In 606,server application 314 establishes an authenticated session with client302. In a particular embodiment, the authenticated session has limitedpermissions/access of API operations for client 302. In 608, serverapplication 314 determines whether upgrading of user 322 from one factorauthentication to two factor authentication is required. If user 322 isdesignated as requiring upgrading from one factor authentication to twofactor authentication, in 610 server application 314 generates a sharedsecret. In 612, server application 314 sends a logon response includingthe shared secret to client 302 using the authenticated session. Inresponse to receiving the shared secret, client 302 generates a one timepasscode (OTP) based upon the shared secret, and sends the OTP generatedbased upon the shared secret to server 304.

In 614, server application 314 receives the OTP from client 302. In 616,server application 314 validates the OTP against the shared secret. Ifthe OTP is validated, in 618 server application 314 stores the sharedsecret in a user profile associated with user 322. In 620, server 304continues the authenticated session in which client 302 is granted fullpermissions/access to API operations to receive access to applicationsand/or services provided by server 304 or another server. In 622, serverapplication 314 sends an authentication response to client 302indicating the continuation of the authenticated session. In theembodiment, subsequent logons from user 322 require user 322 to providethe user ID, password, and a current OTP that is generated based on theshared secret in order to be authenticated with server 304 to gainaccess to applications and/or services provided by server 304 or anotherserver. If in 608, server application 314 determines that two factorauthentication is not required, in 622 server application 314 sends anauthentication response to client 302 indicating that the authenticatedsession may be used by client 302. In such a case in which user 322 isnot upgraded to two factor authentication, subsequent logons from user322 require the providing of only the user ID and password. Serverapplication 314 ends process 600 thereafter.

Thus, a computer implemented method, system or apparatus, and computerprogram product are provided in the illustrative embodiments to enableautomatic upgrade of a user from one step authentication to two stepauthentication and other related features, functions, or operations.Where an embodiment or a portion thereof is described with respect to atype of device, the computer implemented method, system or apparatus,the computer program product, or a portion thereof, are adapted orconfigured for use with a suitable and comparable manifestation of thattype of device.

Where an embodiment is described as implemented in an application, thedelivery of the application in a Software as a Service (SaaS) model iscontemplated within the scope of the illustrative embodiments. In a SaaSmodel, the capability of the application implementing an embodiment isprovided to a user by executing the application in a cloudinfrastructure. The user can access the application using a variety ofclient devices through a thin client interface such as a web browser(e.g., web-based e-mail), or other light-weight client-applications. Theuser does not manage or control the underlying cloud infrastructureincluding the network, servers, operating systems, or the storage of thecloud infrastructure. In some cases, the user may not even manage orcontrol the capabilities of the SaaS application. In some other cases,the SaaS implementation of the application may permit a possibleexception of limited user-specific application configuration settings.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method comprising: transmitting, by a client, auser identifier and a password to a server via an applicationprogramming interface (API); receiving, responsive to a verification ofthe user identifier and password by the server, a logon response ashared secret, wherein the server determines whether the user identifieris to be upgraded from one step authentication to two stepauthentication after successful verification of the user identifier andthe password and grants the client limited permission with respect topermitted API operations and requires the two step authentication foreach subsequent logon attempt; generating, by the client, a one timepasscode (OTP) based upon the shared secret; sending the OTP to theserver via the API, wherein the API includes a Representational statetransfer (REST) API; and granting, responsive to the server validatingthe OTP against the shared secret, a second set of permissions foroperations associated with the API.
 2. The method of claim 1, furthercomprising: receiving, by the client device, the user identifier andpassword, from a user.
 3. The method of claim 1, wherein the receivingof the logon response and shared secret is responsive to a determinationthat a user associated with the user identifier is designated forupgrading from one factor authentication to two factor authentication.4. The method of claim 1, further comprising: storing, by the client,the shared secret within client preferences associated with a user. 5.The method of claim 1, wherein the server is configured to store theshared secret within a user profile associated with a user.
 6. Themethod of claim 1, further comprising: establishing an authenticatedsession with the server, the client having a first set of permissionsfor operations associated with the API;
 7. The method of claim 1,wherein the second set of permissions is greater than the first set ofpermissions.
 8. The method of claim 1, further comprising: transmittingthe user ID, the password, and a current OTP generated based upon theshared secret to the server in a subsequent logon operation.
 9. Acomputer usable program product comprising one or more computer-readablestorage media, and program instructions collectively stored on at leastone of the one or more computer readable storage media, the storedprogram instructions comprising: program instructions to transmit, by aclient, a user identifier and a password to a server via an applicationprogramming interface (API); program instructions to receive, responsiveto a verification of the user identifier and password by the server, alogon response and a shared secret, wherein the server determineswhether the user identifier is to be upgraded from one stepauthentication to two step authentication after successful verificationof the user identifier and the password and grants the client limitedpermission with respect to permitted API operations and requires the twostep authentication for each subsequent logon attempt; programinstructions to generate, by the client, a one time passcode (OTP) basedupon the shared secret; program instructions to send the OTP to theserver via the API, wherein the API includes a Representational statetransfer (REST) API; and program instructions to grant, responsive tothe server validating the OTP against the shared secret, a second set ofpermissions for operations associated with the API.
 10. The computerusable program product of claim 9, further comprising: programinstructions to receive, by the client device, the user identifier andpassword, from a user.
 11. The computer usable program product of claim9, wherein the receiving of the logon response and shared secret isresponsive to a determination that a user associated with the useridentifier is designated for upgrading from one factor authentication totwo factor authentication.
 12. The computer usable program product ofclaim 9, further comprising: program instructions to store, by theclient, the shared secret within client preferences associated with auser.
 13. The computer usable program product of claim 9, wherein theserver is configured to store the shared secret within a user profileassociated with a user.
 14. The computer usable program product of claim9, further comprising: program instructions to establish anauthenticated session with the server, the client having a first set ofpermissions for operations associated with the API.
 15. The computerusable program product of claim 9, wherein the second set of permissionsis greater than the first set of permissions.
 16. The computer usableprogram product of claim 9, further comprising: program instructions totransmit the user ID, the password, and a current OTP generated basedupon the shared secret to the server in a subsequent logon operation.17. The computer usable program product of claim 9, wherein the storedprogram instructions are collectively stored on one or morecomputer-readable storage media in a data processing system, and whereinthe stored program instructions are transferred over a network from aremote data processing system.
 18. The computer usable program productof claim 9, wherein the stored program instructions are collectivelystored on one or more computer-readable storage media in a server dataprocessing system, and wherein the stored program instructions aredownloaded over a network to a remote data processing system for use ina computer readable storage medium associated with the remote dataprocessing system.
 19. A computer system comprising one or moreprocessors, one or more computer-readable memories, one or morecomputer-readable memories, and one or more computer-readable storagemedia, and program instructions collectively stored on at least one ofthe one or more computer-readable storage media for execution by atleast one of the one or more processors via at least one of the one ormore memories, the storage program instructions comprising: programinstructions to transmit, by a client, a user identifier and a passwordto a server via an application programming interface (API); programinstructions to establish an authenticated session with the server, theclient having a first set of permissions for operations associated withthe API; program instructions to receive, responsive to a verificationof the user identifier and password by the server, a logon response anda shared secret, wherein the server determines whether the useridentifier is to be upgraded from one step authentication to two stepauthentication after successful verification of the user identifier andthe password and grants the client limited permission with respect topermitted API operations and requires the two step authentication foreach subsequent logon attempt; program instructions to generate, by theclient, a one time passcode (OTP) based upon the shared secret; programinstructions to send the OTP to the server via the API, wherein the APIincludes a Representational state transfer (REST) API; and programinstructions to grant, responsive to the server validating the OTPagainst the shared secret, a second set of permissions for operationsassociated with the API.
 20. The computer system of claim 19, the storedprogram instructions further comprising: program instructions toreceive, by the client device, the user identifier and password, from auser.